Information centric networking for long term evolution

ABSTRACT

In one embodiment, a method for improving content delivery for a user equipment (UE) is implemented on a computing device and includes: receiving a request from an application layer on the UE, determining whether said request is an ICN-based request using Information Centric Networking (ICN) transport protocol or an IP-based request using Internet Protocol (IP) transport protocol, and for each ICN-based request according to the determining: forwarding the ICN-based request to an ICN function on the UE, and compressing ICN headers in the ICN-based request using robust header (RoHC) compression.

RELATED APPLICATION INFORMATION

The present application claims the benefit of priority from U.S. Provisional Patent Application Ser. No. 62/356,283, filed on Jun. 29, 2016.

FIELD OF THE INVENTION

The present invention generally relates to the deployment of information centric networking (ICN) in long term evolution (LTE) mobile networks.

BACKGROUND OF THE INVENTION

Globally, over 1.3 billion subscribers use Long Term Evolution (LTE) technology, with annual growth of ˜100% annually. Existing LTE networks are based on ‘Global System Mobile Association’ (GSMA), 3rd Generation Partnership Project (3GPP) standards and various specifications providing architectural details. LTE network architectures typically use Internet Protocol (IP) as the main transport protocol for control plane (signaling messages), user plane (content delivery) and management plane (Operations, administration and management functions) communications.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:

FIG. 1 is a simplified schematic illustration of an exemplary ICN enabled LTE architecture, constructed and operative in accordance with embodiments described herein;

FIGS. 2 and 3 are simplified schematic diagrams of exemplary user equipment (UE) protocol stacks for implementing ICN according to the architecture of FIG. 1;

FIGS. 4 and 6 are simplified schematic diagrams illustrating an exemplary mobile base station protocol stack aligned opposite a UE protocol stack, and an exemplary evolved packet core (EPC) protocol stack, according to the architecture of FIG. 1;

FIG. 5 is a simplified schematic diagram which illustrates a logical flow for requests received by a mobile base station from a UE and forwarded to mobile gateway according to the architecture of FIG. 1;

FIG. 7 is a simplified schematic diagram illustrating an exemplary mobile base station protocol stack, aligned opposite a UE protocol stack, and either another mobile base station protocol stack or a Mobility Management Entity (MME) according to the architecture of FIG. 1;

FIG. 8 illustrates a 3GPP protocol configuration field layout; and

FIGS. 9A and 9B illustrate an exemplary attach procedure for a UE according to the architecture of FIG. 1.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

A method for improving content delivery for a user equipment (UE) is implemented on a computing device and includes receiving a request from an application layer on the UE, determining whether said request is an ICN-based request using Information Centric Networking (ICN) transport protocol or an IP-based request using Internet Protocol (IP) transport protocol, and for each ICN-based request according to the determining: forwarding the ICN-based request to an ICN function on the UE, and compressing ICN headers in the ICN-based request using robust header (RoHC) compression.

A method for improving content delivery is performed on a mobile base station and includes: configuring the mobile base station to support ICN transport protocol, and storing content for delivery over the ICN transport protocol in an ICN content cache on the mobile base station.

A method for supporting ICN on a long term evolution (LTE) evolved packet core (EPC) device includes: receiving an initial attach request from a user equipment (UE), where the initial attach request includes an indication of support for ICN transport protocol on the UE, authenticating the UE, creating a session for the UE, where a Packet Data Network (PDN) type is assigned for the session is ICN.

Description

It will be appreciated by persons of ordinary skill in the art that the reliance on IP as the main transport protocol for LTE's user plane may be inefficient primarily due to IP's optimization for layer-3 payload transfer. The optimization for network layer-3 effectively renders IP less efficient for application layer-7 content delivery (offline video, real-time streaming video or time sensitive online gaming etc.). For example, when delivering content in unicast, each mobile unit receives a separate stream from a content server, thereby making redundant use of limited network resources. It will be appreciated that there have been recent advances in multicast and broadcast technologies for content delivery in LTE networks, but actual deployment in the field is limited or considered experimental due to a complex signaling architecture. Furthermore, such technologies require separate frequency spectrums, which are also limited resources in the mobile environment. It will therefore be appreciated that LTE's current architecture may be inefficient and non-optimal for high volume content delivery to mobile devices.

Information Centric Networking (ICN) is a rapidly evolving technology for efficient multimedia content delivery to end devices using Content Delivery Network (CDN) engines, caches, servers, and/or repositories. Existing research and development for ICN has primarily focused on fixed wireline networks and limited wireless networks using Wi-Fi, etc. No specification or standard is currently in use for including ICN in LTE architecture.

It will be appreciated that ICN may remedy some of the deficiencies of IP in an LTE environment. For example, in IP, resource names are transitory, thereby necessitating redundant setup for requests for the same resource from different network entities. In ICN, resource names are persistent, regardless of physical storage location. Accordingly, a given resource may be allocated a unique name that may be used consistently and uniformly throughout a network.

In accordance with embodiments described herein, LTE architecture may therefore be modified to support ICN for content delivery by implementing ICN in mobile user equipments (UEs), base stations (BSs), and/or the evolved packet core (EPC), sometimes referred to as a mobile packet core (MPC). Reference is now made to FIG. 1 which represents a simplified schematic illustration of an exemplary ICN enabled LTE architecture 10, constructed and operative in accordance with embodiments described herein.

FIG. 1 depicts a 3GPP environment, where the control plane uses IP based Non-Access Stratum (NAS) signaling on S-1 Mobility Management Entity (MME), and General Packet Radio Service Tunneling Protocol-Control (GTP-C) messages on S11 interfaces, for mobility management and session management respectively. Similarly, for the user plane, IP based, S1-U, S5, and S8 interfaces are used in unicast for content delivery.

ICN enabled LTE architecture 10 comprises UE protocol stack 100, mobile base station protocol stack 200 (e.g., implemented on an eNodeB as depicted in FIG. 1), Evolved Packet Core/Packet Data Network Gateway (EPC/PGW) protocol stack 300, and CDN 400. As depicted in FIG. 1, in order to improve efficiency for user plane content delivery from ICN enabled CDN 400, ICN may be implemented instead of, or in parallel with EP, as a dual stack protocol stack for a UE and PGW.

As referred to herein, a UE is any type of device which attaches to a cellular network using 3G/UMTS or LTE technologies. The protocols and software stack used inside an LTE capable UE may therefore support both 3G and LTE software inter-working and handover. The latest 3GPP Release 13 (Rel.13) (and subsequent) specifications describe the use of both IP and non-IP protocols to establish logical/session connectivity. In accordance with embodiments described herein, this specified functionality may be leveraged to deploy an ICN protocol stack in a UE.

In accordance with embodiments described herein, ICN may be implemented in a UE by inclusion of a forwarding agent function inserted between the application and network layers. This forwarding agent function may interface with the application layer, and may be configured to provide forwarding decision algorithms to route requests. For example, forwarding decisions may be based on criteria such as application preference (e.g., ICN vs IP transport), content locations, content types, publisher's details, cost, network congestion, quality of service (QoS) and/or any other customizable parameters. For example, the forwarding agent function may, in at least one embodiment, monitor application layer parameters through software probes to discover network status, preference etc. and apply this to forwarding decision algorithms.

For example, ICN may be implemented in a dual stack arrangement in parallel with IP for a UE as represented in UE protocol stack 100. In accordance with embodiments described herein, the UE ICN transport protocol may communicate with either the ICN function in EPC/PGW protocol stack 300 (if, for example, ICN is implemented in the PGW), and/or an ICN function in CDN 400, depending upon how, and to what extent, ICN is implemented in the network.

It will be appreciated by one of ordinary skill in the art that such an arrangement may not require changes to device (i.e., the UE) modem firmware because ICN may be overlaid on top of IP without modification of the native environment. This approach may minimize the resources required to provide ICN functionality while also maintaining full support for legacy IP functionality. Reference is now made to FIG. 2 which is a simplified schematic diagram of an exemplary dual stack UE protocol stack 100 for implementing ICN in parallel with IP for a UE in accordance with embodiments described herein.

UE protocol stack 100 comprises application layer 110, forwarding agent 120, IP function 130, ICN function 140, Packet Data Convergence Protocol (PDCP) 150, Radio Link Control (RLC) 160, Medium Access Control (MAC) 170 and physical layer (PHY L1) 180.

Application layer 110 may refer to the protocol layer for any of a variety of software and/or hardware applications implemented on a UE in system 10, for example, but not limited to, applications for the provision and display of content on the UE. It will be appreciated that the applications in application layer 110 may not be uniformly configured to support the use of a given transport protocol. Specifically, some of the applications may be configured to support the use of IP, some may be configured to support the use of ICN, and some may be configured to support both.

Accordingly, forwarding agent 120 may be configured to route outgoing traffic (e.g., fetch requests from CDN 400, communications with other UEs, etc.) from application layer 110 via either IP function 130 or ICN function 140 based on the capabilities of the originating applications in application layer 110. In accordance with embodiments described herein, forwarding agent 120 may be implemented as a software based router implemented using any suitable mechanism such as, for example, Representational State Transfer (REST), TCP/IP socket and/or Extensible Markup Language (XML), etc.

Forwarding agent 120 may be configured to handle any one of three types of requests from application layer 110: IP-specific, where the application requests IP transport (either because the application doesn't support ICN or has, for whatever reason, been configured to prefer IP); ICN-specific, where the application requests ICN transport (either because the application doesn't support IP or has, for whatever reason, been configured to prefer ICN); or IP/ICN, where the application supports both IP and ICN and allows forwarding agent 120 to determine which transport protocol to use.

Forwarding agent 120 may then forward the application request to either IP function 130 or ICN function 140. It will be appreciated that IP function 130 may represent already existing functionality in the LTE standard, such that minimal changes, if any, may be needed to implement IP function 130 in architecture 10. For example, in accordance with at least one embodiment described herein, forwarding agent 120 may use a TCP/IP socket mechanism to communicate with IP function 130.

It will be appreciated that as described hereinabove, ICN may typically be more efficient than IP, such that forwarding agent 120 may be configured to prefer to route communications through ICN function 140 if a request from application layer 110 does not specify a preference for transport protocol.

In accordance with embodiments described herein, ICN function 140 may forward ICN interest packets and/or data packets using ICN overlay over IP to IP function 130. ICN interest packets are typically packets in which a request for content is included, whereas ICN data packets are response packets including requested content.

It will be appreciated that PDCP 150 may comprise existing PDCP functionality as currently implemented in existing LTE architecture. IP function 130 may therefore forward native IP traffic to PDCP 150, using a known header compression mechanism for IP. In accordance with embodiments described herein, PDCP 150 may also comprise additional functionality to support ICN overlaid over IP. PDCP 150 may also be configured to support header compression for ICN. For example, current PDCP implementations for LTE use robust header compression RoHC) on air interface. In accordance with embodiments described herein, header compression for ICN may be implemented in PDCP 150 using a generally similar RoHC (RFC3095) header compression technique with enhanced algorithms that also support ICN.

It will be appreciated that RLC 160, MAC 170, and PHY L1 180 may be generally unaffected by the implementation of ICN protocol in UE protocol stack 100. Communications received by RLC 160 from PDCP 150 may be in the form of either native IP or ICN over IP; in either case, continued processing with UE protocol stack 100 may be consistent with existing IP only implementations.

In accordance with some embodiments described herein, a UE may be implemented with native ICN functionality to connect to a mobile network, where the mobile network may fetch content from internet/application servers within mobile provider to send some data to UE/application servers. For embodiments in which native ICN functionality is provided, significant changes may be needed in device modem firmware and other software upgrades to support NAS signaling, mobility and/or session management.

Reference is now made to FIG. 3 which is a simplified schematic diagram of an exemplary native ICN UE protocol stack 101 for implementing ICN on a UE in accordance with embodiments described herein. Protocol stack 101 may be generally similar to protocol stack 100 except as noted herein. Accordingly, protocol stack 110 may comprise application layer 110, RLC 160, MAC layer 170 and physical layer 180, each of which may respectively function in a generally similar manner as similarly referenced elements in protocol stack 100.

Protocol stack 101 also comprises forwarding agent 121 and ICN function 140. Forwarding agent 121 may be a modified version of forwarding agent 120 configured to support communication between applications in application layer 110 and ICN function 140. Similar to forwarding agent 120, forwarding agent 121 may be implemented as a software based router implemented using any suitable mechanism such as, for example, Representational State Transfer (REST), TCP/IP socket and/or Extensible Markup Language (XML), etc.

It will be appreciated that similar to the application layer 110 in FIG. 2, the applications installed in application layer 110 of FIG. 3 may be compatible with either IP and/or ICN functionality. Accordingly, forwarding agent 121 may be configured to handle any one of three types of requests from application layer 110: IP-specific, where the application requests IP transport (either because the application doesn't support ICN or has, for whatever reason, been configured to prefer IP); ICN-specific, where the application requests ICN transport (either because the application doesn't support IP or has, for whatever reason, been configured to prefer ICN); or IP/ICN, where the application supports both IP and ICN and allows forwarding agent 121 to determine which transport protocol to use.

Forwarding agent 121 may therefore be operative to forward native ICN-based requests from application layer 110 to ICN function 140. Forwarding agent 121 may also be operative to forward protocol agnostic (i.e., where no transport protocol is specified) requests to ICN function 140. Forwarding agent 121 may also be operative to overlay ICN over IP-based requests and to forward the overlaid requests to ICN function 140.

Protocol stack 101 also comprises PDCP 150, which may be modified to support ICN as in the embodiment of FIG. 2. Accordingly, PDCP 150 may be operative to support both native IP and ICN overlaid over. As discussed with respect to the embodiment of FIG. 2, ICN may be supported using a RoHC (RFC3095) header compression technique having enhanced algorithms to implement ICN.

In accordance with the embodiment of FIG. 3, when the UE connects to a mobile network, the mobile network may employ ICN functionality to fetch content from internet/application servers serviced by the mobile provider to provide data to the UE. In existing, IP-based LTE, when a given UE is powered up, it establishes a radio link connection with a base station and starts attach procedures with the LTE network according to procedures described in the 3GPP Technical Specification (TS) 23.401. Since there is no IP function in the embodiment of FIG. 3, the UE may perform the attach procedures using ICN protocol. For example, the UE may be configured to use a Protocol Configuration Option Information Element (PCO IE) field to communicate its ICN capability during attach procedures.

It will be appreciated that in order to support native ICN functionality for NAS signaling, mobility and/or session management, significant changes may be needed in device modem firmware and software upgrades. Accordingly, in order to limit the impact on NAS signaling—due to dependencies on the Mobility Management Entity (MME), Home Subscriber Server (HSS) and other elements—in accordance with some embodiments described herein, NAS signaling may be maintained using IP, whereas ICN may be implemented and used natively for content delivery.

It will be appreciated that as referred to herein, the term ‘user equipment’ (UE) may be inclusive of devices used to initiate a communication, such as a computer, an electronic device such as a parking meter, vending machine, appliance, Internet of Things (IoT) device, etc., a personal digital assistant (PDA), a laptop or electronic notebook, a cellular telephone, an iPhone™, iPad™, Google Android™ phone, an IP phone, a wearable electronic device, or any other device, component, element, or object capable of initiating voice, audio, video, media, or data exchanges within communication system 10. A UE may also include a suitable interface to a human user such as a microphone, a display, a keyboard, or other terminal equipment. It will further be appreciated that UEs may comprise a processor configured to operate the UE's software, firmware, and/or hardware components.

Reference is now made to FIG. 4 which is a simplified schematic diagram illustrating an exemplary mobile base station protocol stack 200 (e.g., as implemented on an eNB as depicted in FIG. 4) aligned opposite a UE protocol stack 100 and an exemplary EPC protocol stack 300 (e.g., as implemented on an SGW/PGW as depicted in FIG. 4), in accordance with embodiments described herein. Reference is made also to FIG. 5 which illustrates a logical flow for requests received by mobile base station 201 from UE 105 and forwarded to mobile gateway 301. It will be appreciated that UE 105 may be an IP-only UE, or configured with protocol stack 100 or 101 as described with respect to FIGS. 2 and 3; base station 201 may be configured with mobile base station protocol stack 200; and mobile gateway 301 (e.g., an SGW or PGW) may configured with EPC protocol stack 300.

As illustrated in FIG. 5, when UE 105 powers up, it may perform attach procedures using IP protocol to send control messages. Depending on the configuration of UE 105, on successful attachment, UE 105 may have ICN-based identity, IP-based identity, or dual ICN+IP identity. When a user of UE 105 initiates a content request via an application on UE, the request may subsequently be sent to base station 201, and then forwarded to mobile gateway 301 according to the following logic:

If UE 105 sends an ICN request (step 202), base station 201 may forward the request to mobile gateway 301 either using native ICN (if such transport is supported), or ICN as overlay on IP where native ICN support is unavailable.

If UE 105 sends an IP request (step 204), base station 201 may forward the request to mobile gateway 301 using native IP.

UE 105 may also send a non-specified “ICN or IP” request (step 206) accompanied by additional qualifying parameters such as weight, priority, cost, network congestion. It will be appreciated that the additional qualifying parameters may be configurable. Base station 201 may use the parameters to determine the most resource efficient option for forwarding the request from among native IP, native ICN, or ICN over IP, depending on the supported transport

Returning to FIG. 4, protocol stack 200 may be implemented in a mobile base station (e.g. an eNodeB or eNB) and may comprise IP function 230 and ICN function 240 incorporated at the network layer on an S1-U interface between the mobile base station and an EPC element (e.g. SGW or PGW). It will be appreciated that an existing IP based S1-U interface may be modified to support a dual stack with both ICN and IP routing; this interface may be used to carry user plane traffic through a GPRS Transport Protocol (GTP) tunnel to either IP function 330 or ICN function 340 in protocol stack 300. It will be appreciated that in such manner, ICN functionality may be incorporated into protocol stack 200 without disturbing the MAC layer.

When ICN Interest or Data packets are received from a dual stack ICN/IP or native ICN UE (e.g., according to the embodiments of FIGS. 2 and 3), ICN function 240 may be used to process the received packets. If S1-U supports only IP routing, i.e., not ICN, ICN messages may be overlaid on top of IP. Similarly, when an IP-based request for content delivery is received, it will use the standard S1-U interface.

It will be appreciated that the implementation of ICN function 240 in protocol stack 200 may facilitate content caching for local delivery using the ICN transport protocol. It will be appreciated that ICN function 340 in protocol stack 300 is implemented at a SGW or PGW to support ICN based routing for the protocol stack 200 of base station. ICN function 340 may facilitate servicing content cached at the SGW or PGW. Similar ICN functionality may also be implemented at CDN 400.

Reference is now made to FIG. 6 which is a simplified schematic diagram illustrating an exemplary mobile base station protocol stack 200 aligned opposite either UE protocol stack 100 or 101 and an exemplary MME 302, in accordance with embodiments described herein. As will be described with respect to the embodiment of FIG. 6, depending on the configuration of the devices involved, NAS signaling may also be implemented with ICN transport. To implement ICN for NAS signaling and mobility management, the following steps may be performed:

A UE using protocol stack 100 or 101 may send NAS messages using a radio interface. The receiving base station (e.g. eNB) may process the NAS message and forward it to MME 302 using a S1-C interface. The S1-C interface may be configured to support IP, ICN, or dual stack (IP+ICN). If the NAS message was received using ICN protocol, then the base station may process the message and forward it to MME 302 using ICN transport. If ICN transport is not supported between the base station and MME 302, the base station may forward the NAS message using ICN overlay on IP transport. If the NAS message was received using IP protocol, then the base station may process the message and forward it to MME 302 using IP transport.

Reference is now made to FIG. 7 which is a simplified schematic diagram illustrating an exemplary mobile base station protocol stack 200 aligned opposite either UE protocol stack 100 or 101, and either another protocol stack 200 or MME 302, in accordance with embodiments described herein. It will be appreciated that in operation, a UE sends mobility management messages such as location updates, handover requests, etc. Handover requests may be sent when the UE moves or it detects a better signal from another base station. The associated handover messages are processed via either X2 interface (for eNB to eNB handovers), or S1 interface (for eNB to MME/SGW handovers). ICN has built-in functionality to support mobility by re-expressing Interest when the UE moves or detects a better signal from another base station. The following steps may be used to implement ICN for mobility management:

For a handover to MME 302, if a mobility management message is received using ICN protocol, then the base station may process and forward the message to MME 302 using ICN transport via the S1-C interface. If ICN transport is not supported between the base station and MME 302, the base station may forward the message using ICN overlay on IP transport. For a handover to another base station (i.e., eNB to eNB), the base station may send handover control messages as well as user data using ICN protocol via an X2 interface. If ICN is not supported on the X2 interface, then the base station may use ICN overlay over IP transport via the X2 interface.

If the mobility management message is received using IP protocol, the base station may process the message and forward it using IP transport to either MME 302 using S1-C interface, or to another base station using X2 interface. For eNB to eNB handover, both handover control messages and user data may be sent by the base station.

If the mobility management message is received using IP protocol, then the base station may determine which protocol, IP or ICN, to be used. The base station may factor weight, priority, cost, etc. into the determination process.

It will be appreciated that as referred to herein, a base station may include any subset of base station functionalities for a Radio Access Network (RAN), such as for example: NodeB functionalities, Radio Network Controller (RNC) functionalities, Home NodeB (HNB), and base transceiver station (BTS) functionalities for 2nd Generation (2G) and/or 3rd Generation (3G) mobile access network technologies such as Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM (EDGE), radio access network (GERAN), and/or Universal Mobile Telecommunications System (UMTS) Terrestrial radio access network (UTRAN); evolved Node B (eNodeB or eNB) functionalities and/or Home eNodeB (HeNB) functionalities for 4th Generation (4G) LTE mobile access network technologies such as evolved UTRAN (E-UTRAN), 5th Generation (5G) access network base station functionalities; combinations thereof, or the like.

In general, the Evolved Packet Core (EPC) provides session management functionality for a UE. When a UE is powered-on, it performs NAS signaling and after successful authentication it attaches with either a PGW for LTE networks or a Gateway GPRS Support Node (GGSN) for 3G cellular network. The PGW or GGSN is the anchoring point for the UE and is responsible for service creations, authorization, session maintenance, eventual termination upon UE power-off, etc. In accordance with embodiments described herein, ICN functionality may be implemented in the EPC.

Returning to FIG. 1, ICN function 340 may be inserted at the session management layer of protocol stack 300 in parallel with existing IP functionality. The session management layer is used for performing attach procedures and assigning a logical identity to the UE user. After successful authentication by HSS, the MME may send a Create Session Request (CSR) to the SGW, and the SGW may send the CSR to the PGW.

In accordance with embodiments described herein, a CSR may be enhanced to include a Protocol Configuration Option Information Element (PCO IE), which may be used to indicate ICN support by the UE providing the request, according to the embodiments of FIGS. 3 and 4.

For a dual stack UE (e.g., the UE of FIG. 3), the PGW may support attachment in terms of both IP and ICN based transport; the UE name may be registered and used for session management. For an ICN capable UE, the PGW may be configured to provide ICN attachment. For a native IP UE, the PGW may use known IP functionality for attachment.

It will be appreciated that in accordance with embodiments described herein, ICN function 340 may be configured with full ICN functionality, such as, for example, forwarding capabilities (e.g., Content Store (CS), Pending Interest Table (PIT) and Forwarding Information Base (FIB) tables). In accordance with at least one embodiment, the PGW may cache contents locally according to ICN protocol using CS functionality provided therein.

Reference is now made to FIG. 8 which illustrates a 3GPP protocol configuration field layout 400 that may be leveraged to provide support for ICN in LTE according to embodiments described herein.

Octet 3, as denoted by reference numeral 410, may be used to carry configuration protocol information (where configuration protocols define a PDN type) which may be enhanced to contain details about IP (either IPv4, IPv6, or both) or ICN. Furthermore, combinations of Octet 4 to Z, as denoted by reference numeral 420, may be used to provide additional information related to ICN capability. The PCO IE parameter (as discussed hereinabove) may be matched between UE and EPC gateways (e.g., MME, SGW, PGW) so that a UE may attach successfully.

Reference is now made to FIGS. 9A and 9B which together illustrate an attach procedure according to 3GPP TS 23.401 V13.61 (2016-03) section 5.3.2.1. In accordance with embodiments described herein, steps 1 and 12-22 may be enhanced to include additional parameters to facilitate ICN implementation. As described hereinabove, ICN capability may be indicated in a PCO IE using a Tag Length Value (TLV) format. Enhanced functionality may be added to the existing steps of the attach procedure to support enhanced ICN capabilities in a PGW in addition to normal IP attach procedures.

At Step 1, a given UE may send an initial attach request. If the UE is ICN capable, the initial attach request may include the PCO IE field populated with an indication of ICN capability. Once the attach request is successful, the PGW assigns an address for the UE. For an IP-based UE, i.e., PDN=IP, the PGW may assign either an IPv4 or IPv6 (Link local) address in the create session request (CSR) in step 13. For PDN type=ICN, the PGW will register the UE with a name according to the ICN protocol. This ICN-based name may then be used for the creation of session and context related functions (e.g., billing, mediation, enhanced charging function/deep packet inspection, lawful intercept, etc.) for the UE during the session.

As referred to herein, an EPC may include one or more mobile gateways hosting any or all functionalities for any combination of: Serving Gateway (SGW), Serving General Packet Radio Service (GPRS) Support Node (SGSN), Packet Data Network (PDN) Gateway (PGW), and/or Gateway GPRS Support Node (GGSN) operations. Traditionally, an SGW is a data-plane element that can provide functionality for managing user mobility and interfaces with RAN nodes (e.g., eNodeBs, NodeBs, HeNBs, HNBs, etc.). An SGW may also maintain data paths between RAN nodes and one or more PGWs. A PGW typically provides IP connectivity access network (IP-CAN) session connectivity for UEs to external Packet Data Networks (PDNs) (e.g., the Internet).

As referred to herein in this Specification, the terms ‘user’, ‘subscriber’, ‘UE’ and ‘user/UE’ can be used interchangeably. It should be understood that a user, or more particularly, a subscriber, can be associated with the operation of a corresponding UE for one or more voice and/or data sessions. In various embodiments, a subscriber associated with a given UE can be identified using one or more identifiers such as, for example, an International Mobile Subscriber Identity (IMSI) or a Temporary IMSI (T-IMSI). An IMSI for a given subscriber is typically stored on a Subscriber Identity Module (SIM) (e.g., a SIM card) within the subscriber's UE.

It is appreciated that software components of the present invention may, if desired, be implemented in ROM (read only memory) form. The software components may, generally, be implemented in hardware, if desired, using conventional techniques. It is further appreciated that the software components may be instantiated, for example: as a computer program product or on a tangible medium. In some cases, it may be possible to instantiate the software components as a signal interpretable by an appropriate computer, although such an instantiation may be excluded in certain embodiments of the present invention.

It is appreciated that various features of the invention which are, for clarity, described in the contexts of separate embodiments may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment may also be provided separately or in any suitable subcombination.

It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather the scope of the invention is defined by the appended claims and equivalents thereof: 

What is claimed is:
 1. A user equipment (UE) comprising: a processor; and a protocol stack operative to be used by said processor comprising: an application layer, an Information Centric Networking (ICN) transport function operative to indicate in an initial attach request sent by said UE that said UE is ICN capable by inserting an ICN indication in a Protocol Configuration Option Information Element (PCO IE) field in said initial attach request, a forwarding agent, wherein said forwarding agent is operative to receive ICN-based requests and Internet Protocol (IP) based requests from said application layer, and to forward said ICN-based requests to said ICN transport function, and a Packet Data Convergence Protocol (PDCP) operative to receive said ICN-based requests from said ICN transport function, and forward said ICN-based requests to a Radio Link Control (RLC) protocol.
 2. The UE according to claim 1 and wherein said protocol stack further comprises: an IP transport function implemented in parallel to said ICN transport function, wherein: said forwarding agent is further operative to forward said IP based requests to said IP transport function; said ICN transport function is operative to forward said ICN-based requests to said IP transport function; and said IP transport function is operative to forward said ICN-based requests as ICN over IP to said PDCP.
 3. The UE according to claim 2 and wherein said forwarding agent is further operative to: receive ICN+IP requests from said application layer, wherein said ICN+IP requests are associated with both said ICN transport protocol and said IP transport protocol; determine a preferred transport protocol from among said ICN transport protocol and said IP transport protocol according to parameters for limiting network resource usage; and forward said ICN+IP requests according to said preferred transport protocol.
 4. The UE according to claim 1 and wherein: said ICN transport function is implemented as native ICN without implementation of an IP transport function in said protocol stack; and said forwarding agent is operative to send said IP based requests to said ICN transport function.
 5. The UE according to claim 1 and wherein said PDCP is further operative to use robust header (RoHC) compression to compress headers in said ICN-based requests.
 6. The UE according to claim 1 and wherein Non-Access Stratum (NAS) signaling for said UE is IP-based.
 7. The UE according to claim 1 and wherein said UE is operative to communicate via a Long Term Evolution (LTE) network.
 8. A method for improving content delivery for a user equipment (UE), the method implemented on a computing device and comprising: indicating in an initial attach request sent by said UE that said UE is Information Centric Networking (ICN) capable by inserting an ICN indication in a Protocol Configuration Option Information Element (PCO IE) field in said initial attach request; receiving a request from an application layer on said UE; determining whether said request is an ICN-based request using Information Centric Networking (ICN) transport protocol or an IP-based request using Internet Protocol (IP) transport protocol; and upon determining that said request comprises an ICN-based request: forwarding said ICN-based request to an ICN transport function on said UE, and compressing ICN headers in said ICN-based request using robust header (RoHC) compression.
 9. The method according to claim 8 and further comprising: receiving content from a content distribution network (CDN) via said ICN transport protocol.
 10. The method according to claim 9 and wherein said receiving content comprises receiving said content from a cache on an ICN-enabled mobile base station.
 11. The method according to claim 9 and wherein said receiving content comprises receiving said content from a cache on an ICN-enabled evolved packet core (EPC) gateway.
 12. The method according to claim 9 and wherein said content is received from an ICN multicast to more than one said UE.
 13. The method according to claim 8 and wherein said initial attach request is associated with attaching to a Long Term Evolution (LTE) mobile network.
 14. The method according to claim 8 and further comprising receiving an assigned ICN name upon success of said initial attach request.
 15. The method according to claim 8 and further comprising overlaying said ICN-based request over said IP transport protocol, wherein said UE is implemented with support for both said ICN transport protocol and said IP transport protocol.
 16. The method according to claim 8 and further comprising: using said ICN transport protocol for content delivery; and using said IP transport protocol for Non-Access Stratum (NAS) signaling.
 17. The method according to claim 8 and wherein: said receiving comprises receiving ICN+IP requests from said application layer, wherein said ICN+IP requests are associated with both said ICN transport protocol and said IP transport protocol; and said determining comprises determining a preferred transport protocol from among said ICN transport protocol and said IP transport protocol according to parameters for limiting network resource usage.
 18. A user equipment (UE) comprising: a memory; and a processor coupled the memory, the processor operable for: indicating in an initial attach request sent by said UE that said UE is Information Centric Networking (ICN) capable by inserting an ICN indication in a Protocol Configuration Option Information Element (PCO IE) field in said initial attach request; receiving a request from an application layer on said UE; determining whether said request is an ICN-based request using Information Centric Networking (ICN) transport protocol or an IP-based request using Internet Protocol (IP) transport protocol; forwarding each said ICN-based request to an ICN function on said UE; and compressing ICN headers in said each ICN-based request using robust header (RoHC) compression. 